S3Drive - Bug: Rename Folder Glitch

Sometimes when renaming the folder glitches like if you open it, It's endless until you won't be able to open it again. It just randomly happens even in Mobile.

Thanks for your report. What's your S3 provider? Does it fix itself when you refresh the listings? (edited)

Tom

Thanks for your report. What's your S3 provider? Does it fix itself when you refresh the listings? (edited)

It happened on Storj and iDrive and no it does not. I tried anything like renaming back, moving it back n forth but to no avail so I just downloaded the folder in hope to still download the files and it did (edited)

10:18 PM

Then deleted the folder and uploaded again

Does it happen consistently? This isn't something we can reproduce on our end. By any chance can you provide us some steps, so we can reproduce it? We've had similar bug in the past, that was related when rename was done to newly created file/folder entry. Temporary solution before we've fixed that was to refresh view after file/folder was created.

Tom

Does it happen consistently? This isn't something we can reproduce on our end. By any chance can you provide us some steps, so we can reproduce it? We've had similar bug in the past, that was related when rename was done to newly created file/folder entry. Temporary solution before we've fixed that was to refresh view after file/folder was created.

It happens rarely and I can't seem to reproduce it now sasukestare

but what I noticed is that It happens only when renaming folders with a dot.

11:42 PM

Like from the video .archived

11:44 PM

I tried a lot of random stuff and seems like I can reproduce it (same issue) but different way by 1. Uploading a big file. 2. While file is uploading, rename the folder to something else. (edited)

It seems we still can't reproduce that. We've created test folder with 6 small files and 1 big file and then moved it to top of the files. Once at least one small file was uploaded, the directory appeared on the UI. We've then decided to rename directory from .folder to .folder2. Rename affected only already uploaded small files. After couple seconds when big file was uploaded, the: .folder appeared once again, since this was the folder that was originally used for upload request.

Tom

It seems we still can't reproduce that. We've created test folder with 6 small files and 1 big file and then moved it to top of the files. Once at least one small file was uploaded, the directory appeared on the UI. We've then decided to rename directory from .folder to .folder2. Rename affected only already uploaded small files. After couple seconds when big file was uploaded, the: .folder appeared once again, since this was the folder that was originally used for upload request.

Hmm that's weird. Here I managed to reproduced it again perhaps the information I provided about the issue lacks

, please see. (edited)

I2rys (安全)

Hmm that's weird. Here I managed to reproduced it again perhaps the information I provided about the issue lacks

, please see. (edited)

Thanks for this video. I can clearly see the issue, however we couldn't find any feasible scenario where this would happen as a bug on the S3Drive side. Instead, we've found a possible scenario that involves broken response coming from the S3 provider. In a next S3Drive version we will add: Debug log option, which after enabling would store more information in the application Logs which would allow us to confirm our claims. Can you please let me know if that was Storj or iDrive E2 or any other provider? Was bucket versioning enabled or any other settings (e.g. server side encryption) enabled on the provider's admin panel? (edited)

1

Tom

Thanks for this video. I can clearly see the issue, however we couldn't find any feasible scenario where this would happen as a bug on the S3Drive side. Instead, we've found a possible scenario that involves broken response coming from the S3 provider. In a next S3Drive version we will add: Debug log option, which after enabling would store more information in the application Logs which would allow us to confirm our claims. Can you please let me know if that was Storj or iDrive E2 or any other provider? Was bucket versioning enabled or any other settings (e.g. server side encryption) enabled on the provider's admin panel? (edited)

Hmm I see, I was using iDrive E2 and

Bucket Versioning: Disabled
Server Side Encryption: Enabled
S3Drive Encryption: Enabled
Multiform: Enabled

That's pretty much all in settnigs.

1

Hi again, can you please update your version to 1.9.6 and then enable: "Debug logs" in the settings and try to reproduce this issue? It would then be interesting to see the log entry similar to this, which would help us to understand whether iDrive E2 provided malformed response or perhaps issue is elsewhere. Thanks!

Tom

Hi again, can you please update your version to 1.9.6 and then enable: "Debug logs" in the settings and try to reproduce this issue? It would then be interesting to see the log entry similar to this, which would help us to understand whether iDrive E2 provided malformed response or perhaps issue is elsewhere. Thanks!

Hello sorry for late response. I reproduced it again and these are the messages in logs (edited)

6:58 AM

Btw is it just me or S3drive doesn't automatically check updates and notify?

7:04 AM

I2rys (安全)

Hello sorry for late response. I reproduced it again and these are the messages in logs (edited)

Yep, so issue is now visible at least. There maybe couple issues here, but the effects of it are visible only on iDrive E2 as far we're concerned. It seems that for some reason entry with double slash at the end was created. This makes iDrive E2 to return a folder itself ending with: \ which we strip (as no folder should contain slash in the name, and that then translates to itself. We could possibly fix it on the S3Drive side, by simply skipping \ entry, so if you've clicked the folder it would become empty instead of being a "link" to itself. Were there any other folders/files expected in that folder that for some reason weren't displayed correctly? Or the issue is purely about folder entry that loops itself? Did you reproduce this issue solely using S3Drive? Was it caused during rename in a similar way as on the attached video? For some reason double slash was created. In most cases this is handled by S3 APIs correctly, but it seems iDrive E2 doesn't handle that. To improve app resilience we need to find a place which caused to double slash creation in first place. Thank you for your input so far, it's extremely helpful!

I2rys (安全)

Click to see attachment 🖼️

We set up these notifications manually and don't always update it. We do it usually every couple minor releases or after stable major release is there.

1

Hi, I have also the same problem in v.1.9.6 (provider: Storj). I just opened a "test" folder, then added a picture in it. When I renamed the folder as "test12", the picture was removed and there was endless loop of folders with the name "test12".

Tom

Yep, so issue is now visible at least. There maybe couple issues here, but the effects of it are visible only on iDrive E2 as far we're concerned. It seems that for some reason entry with double slash at the end was created. This makes iDrive E2 to return a folder itself ending with: \ which we strip (as no folder should contain slash in the name, and that then translates to itself. We could possibly fix it on the S3Drive side, by simply skipping \ entry, so if you've clicked the folder it would become empty instead of being a "link" to itself. Were there any other folders/files expected in that folder that for some reason weren't displayed correctly? Or the issue is purely about folder entry that loops itself? Did you reproduce this issue solely using S3Drive? Was it caused during rename in a similar way as on the attached video? For some reason double slash was created. In most cases this is handled by S3 APIs correctly, but it seems iDrive E2 doesn't handle that. To improve app resilience we need to find a place which caused to double slash creation in first place. Thank you for your input so far, it's extremely helpful!

Hmm I tried on Storj and Backblaze B2 (issue persists) so I don't think It's iDrive E2 only.

Were there any other folders/files expected in that folder that for some reason weren't displayed correctly? The folder entry simply loops itself thus the folder files won't even show
Did you reproduce this issue solely using S3Drive (rename)? After conducting further tests I can also reproduce it with move and copy not just rename. But overall It's the same issue, it's the double slash. ;-;

(edited)

I2rys (安全)

Hmm I tried on Storj and Backblaze B2 (issue persists) so I don't think It's iDrive E2 only.

Were there any other folders/files expected in that folder that for some reason weren't displayed correctly? The folder entry simply loops itself thus the folder files won't even show
Did you reproduce this issue solely using S3Drive (rename)? After conducting further tests I can also reproduce it with move and copy not just rename. But overall It's the same issue, it's the double slash. ;-;

(edited)

Hey, we've managed to reproduce it on Storj and iDrive E2 (bucket versioning disabled. Previously we couldn't reproduce it on iDrive E2, as we've confused settings with this issue: https://discord.com/channels/1069654792902815845/1260374351115456615 and used Versioning enabled instead of disabled. We aren't finding this issue on Backblaze B2 regardless of versioning settings. Having said that, since we can reproduce the issue, we will now work on the fix, which we hope to include in a next release. Thanks for your feedback so far and stay tuned!

1

This shall be now resolved in 1.9.7 already available on desktop. It will be released to mobile today/tomorrow. Additionally we've added corruption fixer, so if you have an existing "broken" folder, you can rename it again in order to display its file contents properly. It's not that data is lost, it's just with // (double slash` it's not properly browsable within S3Drive. I would be keen to know if this has helped to resolve your issue. (edited)

1

Tom

This shall be now resolved in 1.9.7 already available on desktop. It will be released to mobile today/tomorrow. Additionally we've added corruption fixer, so if you have an existing "broken" folder, you can rename it again in order to display its file contents properly. It's not that data is lost, it's just with // (double slash` it's not properly browsable within S3Drive. I would be keen to know if this has helped to resolve your issue. (edited)

Thank you so much Tom! I can now rename my files properly without downloading and uploading instead skull_blush

1

10:47 AM

I can confirm that the issue has been fixed!